local tests:

Finished in 354.52 seconds
2361 specs, 0 failures

but I do see the

Warning: writing junit report failed for '', 'TEST-alloygenerate.xml'. Reasons:
  Rhino attempt: java is not defined
  PhantomJs attempt: window is not defined
  NodeJS attempt: ENOENT: no such file or directory, mkdir

messages too.

Where are they generated in the first place? Would be better to not even generate them instead of manually fixing it down the road

This one: https://github.com/tidev/alloy/blob/master/Alloy/commands/compile/ast/controller.js#L48 is the last code that is run in Alloy which produces the newlines. I can add .trim() there already and the new lines are gone too. So babel is adding newlines somewhere.

Having the .trim() in the compile/index file was a bit of a "safety" spot in case the other methods in the AST controller produced newlines too.

ohhhh. I just saw that there is an option retainLines (https://github.com/tidev/alloy/blob/master/Alloy/commands/compile/ast/controller.js#L10) and it's true because of: #904
That will keep the new lines for debugging purposes. Sadly the ticket is not there https://jira-archive.titaniumsdk.com/TIMOB-19848 (guess it was private)

@hansemannn now I pass deployType == production as a parameter to the AST compiler and only for a production build I will set retainLines to false.

To test it: build a dev build and check /Resources/android/alloy/controllers/index.js and build a dist build. Empty lines will be removed when you do a dist build